|
|
|
|
|
|
|
The most important project activity you'll engage in with either Rational Rose/Visual Basic or Visual Modeler is the creation of architecture models, diagrams, and documentation. In addition, you'll be able to create the necessary class modules and class utilities (or general code modules) to support the evolving system architecture as you iterate and increment through the various project phases. With either tool, you can also reverse-engineer an existing Visual Basic project, thereby automatically creating a model. |
|
|
|
|
|
|
|
|
The Importance of Traceability |
|
|
|
|
|
|
|
|
Traceability is that attribute of a project artifact that enables following business-related entity classes from the actual code to the lowest class models up to the high analysis models and the project documentation itself. Master test cases and test scripts also refer to the same class, object, and actor names as other artifacts of the project life cycle. Unfortunately, too many projects give little attention to the necessity of traceability. It might seem like extra work, but make sure to keep all artifacts (documents, models, diagrams, and code files) in sync when it comes to business domain terminology. Failing to do so very often results in unnecessary confusion and stress down the road. |
|
|
|
|
|
|
|
|
The Design-View Class Model |
|
|
|
|
|
|
|
|
When you begin modeling your classes in the design phase, the resulting models will become more detailed with each iteration. Figure 3.1 shows how your class model from the analysis phase now appears. |
|
|
|
|
|
|
|
|
Figure 3.1.
The updated class model has two more classes because of your new
discoveries about the domain. Notice that traceability is still
evident. |
|
|
|
|
|
